Working with iParts

An iPart is an iMIS-specific web part that represents a building block of features that you can place on a content record with other building blocks to create new pages of features. You can combine and display multiple iParts in a content record, as you prefer.

Default iParts appear throughout iMIS. You can modify them for your needs and you can reuse iParts throughout the system.

Working with iParts is just one part of managing your organization’s website. For more on creating content and building web pages, see these topics:

■    Concept: content records, iParts, and content types

■    Concept: sitemaps and navigation items

■    Concept: Surf-to-Edit

■    Managing content records

■    Defining sitemaps (navigation items)

■    Defining shortcut URLs

■    Content Management Fields

Configuration

After adding an iPart to a content record, configuring it allows you to:

■    Define how the iPart will behave

■    Control how much access you want end users to have

■    Hide some options from end users; two instances of the same iPart with different configurations can appear as two different controls to the end user

■    Examples:

□    Allow users to edit on a staff-facing site, but display the data in read-only mode on a public-facing site

□    Use multiple instances of an iPart on one page to access different sets of data

Run-time versus design-time

iParts have two different views:

■    Design-time view: What you see in a content record when you add an iPart and configure it.

■    Run-time view: What your end-user sees when viewing the iPart within your website. This may differ from what you see in the Design-time view, because some iParts have a different behavior after you publish the content.